_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 4f242cb}

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 0b85f6e}

LGTM!

Two critical regressions stand out: the replacement HTTP factory in FeatureFlagsBackend loses both send-once semantics (risking duplicate exposure/evaluation counts on retries) and the DD-EVP-ORIGIN/DD-EVP-ORIGIN-VERSION identity headers (silently dropping SDK attribution). Additionally, a permanent resolved=true flag in EventProxy after a failed Agent discovery prevents any recovery of event pipelines even after the Agent comes back online.

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 75cccf3}

Findings that could not be posted inline

products/feature-flagging/feature-flagging-lib/src/main/java/com/datadog/featureflag/EventProxy.java:81

Allow event delivery to recover after failed discovery

If initial Agent discovery fails, both clients can be null, yet resolved permanently prevents another attempt. JavaAgentBridge then returns no transport, causing FeatureFlagsRuntime to omit both event pipelines when direct delivery is unavailable. Agent recovery cannot restore reporting, even after provider recreation because the backend retains the cached absence. Keep a recoverable transport and pipelines alive, and re-probe unavailable routes; changing this flag alone is insufficient.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

_{🤖 Bits Code Review · Open Bits AI session}

products/feature-flagging/feature-flagging-lib/src/main/java/com/datadog/featureflag/FeatureFlagsBackend.java:36

Preserve send-once semantics for proxied event batches

If the proxy accepts a batch but its response times out, this factory permits replaying the same exposure or evaluation counts. The two-argument constructor defaults to sendOnce=false, enabling timeout/5xx retries on the no-fallback path and leaving OkHttp automatic retries enabled even with NEVER_RETRY. This regresses the previous transport's send-once safeguards and can inflate event counts. Enable send-once semantics on the factory.

            new BackendApiFactory(config, sco, true),

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

_{🤖 Bits Code Review · Open Bits AI session}

products/feature-flagging/feature-flagging-lib/src/main/java/com/datadog/featureflag/FeatureFlagsBackend.java:36

Keep SDK identity headers on proxied Feature Flags events

Every proxied exposure and evaluation batch now uses a factory with empty request headers, and EvpProxyApi does not supply DD-EVP-ORIGIN or DD-EVP-ORIGIN-VERSION itself. The removed factory supplied both, so successful deliveries silently lose SDK identity and version attribution. Restore those headers and the corresponding forwarding-capability check during proxy discovery.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

_{🤖 Bits Code Review · Open Bits AI session}